Registry Guide for Windows Registry Guide for Windows
Part of the WinGuides Network
WinGuides Network and Software
Registry tweaks, tricks & hacks to optimize, enhance and secure Microsoft Windows.

Manage the Domain Controller Cannot Be Reached Message (Windows NT/2000/XP)
Category: Home > Network

Download this tweak with Tweak Manager!This tweak can be easily applied using WinGuides Tweak Manager.
Download a free trial now!

When Windows is unable to contact a domain controller during a users login a popup error message may be displayed, this message can be controlled by modifying this setting.

To control the following message:

A domain controller for your domain could not be contacted. You have been logged on using cached account information. Changes made to your profile since you last logged on may not be available.

Per User Parameter

Open your registry and find the key below.

Create a new DWORD value, or modify the existing value, named 'ReportDC' and set it to equal '0' to suppress the message.

System-Wide Parameter

On Windows 2000 and above this message is supressed by default, to modify it open your registry and find the key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \Windows NT\CurrentVersion\Winlogon]

Create a new string value called "ReportControllerMissing" and set it to "TRUE" to report errors, or "FALSE" to suppress errors.

Restart Windows for the change to take effect.

Registry Editor Example
|NameTypeData|
|(Default)REG_SZ(value not set)|
|ReportDCREG_DWORD0x00000001 (1)|
|ReportControllerMissingREG_SZTRUE|
-
|HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon|
-

Settings:
User Key: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
Name: ReportDC, ReportControllerMissing
Type: REG_DWORD (DWORD Value)
Value: (0 = message is suppressed, 1 = message is not suppressed)

Disclaimer: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.

Last Modified: March 26, 2002

 Return to Index Copyright © 1998-2003. All Rights Reserved.  License